Resource skipping for multiple grants

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may select first resources to skip in each grant occasion of multiple grant occasions for communications on a physical uplink channel. The UE may transmit uplink control information (UCI) that indicates the first resources or second resources that are not to be skipped in each grant occasion of the multiple grant occasions. The UE may transmit the communications in the multiple grant occasions using the second resources and not the first resources. Numerous other aspects are described.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication and to techniques and apparatuses for skipping resourcesfor multiple grants.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, or the like). Examples of such multiple-accesstechnologies include code division multiple access (CDMA) systems, timedivision multiple access (TDMA) systems, frequency division multipleaccess (FDMA) systems, orthogonal frequency division multiple access(OFDMA) systems, single-carrier frequency division multiple access(SC-FDMA) systems, time division synchronous code division multipleaccess (TD-SCDMA) systems, and Long Term Evolution (LTE).LTE/LTE-Advanced is a set of enhancements to the Universal MobileTelecommunications System (UMTS) mobile standard promulgated by theThird Generation Partnership Project (3GPP).

A wireless network may include one or more base stations that supportcommunication for a user equipment (UE) or multiple UEs. A UE maycommunicate with a base station via downlink communications and uplinkcommunications. “Downlink” (or “DL”) refers to a communication link fromthe base station to the UE, and “uplink” (or “UL”) refers to acommunication link from the UE to the base station.

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent UEs to communicate on a municipal, national, regional, and/orglobal level. New Radio (NR), which may be referred to as 5G, is a setof enhancements to the LTE mobile standard promulgated by the 3GPP. NRis designed to better support mobile broadband internet access byimproving spectral efficiency, lowering costs, improving services,making use of new spectrum, and better integrating with other openstandards using orthogonal frequency division multiplexing (OFDM) with acyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and/orsingle-carrier frequency division multiplexing (SC-FDM) (also known asdiscrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, aswell as supporting beamforming, multiple-input multiple-output (MIMO)antenna technology, and carrier aggregation. As the demand for mobilebroadband access continues to increase, further improvements in LTE, NR,and other radio access technologies remain useful.

SUMMARY

Some aspects described herein relate to a method of wirelesscommunication performed by a user equipment (UE). The method may includeselecting first resources to skip in each grant occasion of multiplegrant occasions for communications on a physical uplink channel. Themethod may include transmitting uplink control information (UCI) thatindicates the first resources or second resources that are not skippedin each grant occasion of the multiple grant occasions. The method mayinclude transmitting the communications in the multiple grant occasionsusing the second resources and not the first resources.

Some aspects described herein relate to a method of wirelesscommunication performed by a network entity. The method may includereceiving UCI that indicates first resources or second resources ofmultiple grant occasions, the first resources in each grant occasionbeing first for communications on a physical uplink channel and thesecond resources not being skipped. The method may include receiving thecommunications in the multiple grant occasions. The method may includedecoding the communications in the second resources and not decoding thecommunications in the first resources based at least in part on the UCI.

Some aspects described herein relate to a UE for wireless communication.The UE may include a memory and one or more processors coupled to thememory. The one or more processors may be configured to select firstresources to skip in each grant occasion of multiple grant occasions forcommunications on a physical uplink channel. The one or more processorsmay be configured to transmit UCI that indicates the first resources orsecond resources that are not to be skipped in each grant occasion ofthe multiple grant occasions. The one or more processors may beconfigured to transmit the communications in the multiple grantoccasions using the second resources and not the first resources.

Some aspects described herein relate to a network entity for wirelesscommunication. The network entity may include a memory and one or moreprocessors coupled to the memory. The one or more processors may beconfigured to receive UCI that indicates first resources or secondresources of multiple grant occasions, the first resources in each grantoccasion being first for communications on a physical uplink channel andthe second resources not being skipped. The one or more processors maybe configured to receive the communications in the multiple grantoccasions. The one or more processors may be configured to decode thecommunications in the second resources and not decode the communicationsin the first resources based at least in part on the UCI.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a UE. The set of instructions, when executed by one ormore processors of the UE, may cause the UE to select first resources toskip in each grant occasion of multiple grant occasions forcommunications on a physical uplink channel. The set of instructions,when executed by one or more processors of the UE, may cause the UE totransmit UCI that indicates the first resources or second resources thatare not to be skipped in each grant occasion of the multiple grantoccasions. The set of instructions, when executed by one or moreprocessors of the UE, may cause the UE to transmit the communications inthe multiple grant occasions using the second resources and not thefirst resources.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a network entity. The set of instructions, whenexecuted by one or more processors of the network entity, may cause thenetwork entity to receive UCI that indicates first resources or secondresources of multiple grant occasions, the first resources in each grantoccasion being skipped for communications on a physical uplink channeland the second resources not being skipped. The set of instructions,when executed by one or more processors of the network entity, may causethe network entity to receive the communications in the multiple grantoccasions. The set of instructions, when executed by one or moreprocessors of the network entity, may cause the network entity to decodethe communications in the second resources and not decode thecommunications in the first resources based at least in part on the UCI.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for selecting firstresources to skip in each grant occasion of multiple grant occasions forcommunications on a physical uplink channel. The apparatus may includemeans for transmitting UCI that indicates the first resources or secondresources that are not to be skipped in each grant occasion of themultiple grant occasions. The apparatus may include means fortransmitting the communications in the multiple grant occasions usingthe second resources and not the first resources.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for receiving UCI thatindicates first resources or second resources of multiple grantoccasions, the first resources in each grant occasion being first forcommunications on a physical uplink channel and the second resources notbeing skipped. The apparatus may include means for receiving thecommunications in the multiple grant occasions. The apparatus mayinclude means for decoding the communications in the second resourcesand not decoding the communications in the first resources based atleast in part on the UCI.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, network entity, wireless communication device, and/orprocessing system as substantially described herein with reference toand as illustrated by the drawings and specification.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages, will be betterunderstood from the following description when considered in connectionwith the accompanying figures. Each of the figures is provided for thepurposes of illustration and description, and not as a definition of thelimits of the claims.

While aspects are described in the present disclosure by illustration tosome examples, those skilled in the art will understand that suchaspects may be implemented in many different arrangements and scenarios.Techniques described herein may be implemented using different platformtypes, devices, systems, shapes, sizes, and/or packaging arrangements.For example, some aspects may be implemented via integrated chipembodiments or other non-module-component based devices (e.g., end-userdevices, vehicles, communication devices, computing devices, industrialequipment, retail/purchasing devices, medical devices, and/or artificialintelligence devices). Aspects may be implemented in chip-levelcomponents, modular components, non-modular components, non-chip-levelcomponents, device-level components, and/or system-level components.Devices incorporating described aspects and features may includeadditional components and features for implementation and practice ofclaimed and described aspects. For example, transmission and receptionof wireless signals may include one or more components for analog anddigital purposes (e.g., hardware components including antennas, radiofrequency (RF) chains, power amplifiers, modulators, buffers,processors, interleavers, adders, and/or summers). It is intended thataspects described herein may be practiced in a wide variety of devices,components, systems, distributed arrangements, and/or end-user devicesof varying size, shape, and constitution.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can beunderstood in detail, a more particular description, briefly summarizedabove, may be had by reference to aspects, some of which are illustratedin the appended drawings. It is to be noted, however, that the appendeddrawings illustrate only certain typical aspects of this disclosure andare therefore not to be considered limiting of its scope, for thedescription may admit to other equally effective aspects. The samereference numbers in different drawings may identify the same or similarelements.

FIG. 1 is a diagram illustrating an example of a wireless network, inaccordance with the present disclosure.

FIG. 2 is a diagram illustrating an example of a network entity (e.g.,base station) in communication with a user equipment (UE) in a wirelessnetwork, in accordance with the present disclosure.

FIG. 3 is a diagram illustrating an example of a disaggregated basestation, in accordance with the present disclosure.

FIG. 4 is a diagram illustrating an example of a slot format, inaccordance with the present disclosure.

FIG. 5 is a diagram illustrating an example of uplink configured grantcommunication, in accordance with the present disclosure.

FIG. 6 is a diagram illustrating an example of skipping a communicationassociated with a grant, in accordance with the present disclosure.

FIG. 7 is a diagram illustrating an example of skipping resources of agrant, in accordance with the present disclosure.

FIG. 8 is a diagram illustrating an example of a skipping indication, inaccordance with the present disclosure.

FIG. 9 is a diagram illustrating an example of skipping indications, inaccordance with the present disclosure.

FIG. 10 is a diagram illustrating an example of skipping indications, inaccordance with the present disclosure.

FIG. 11 is a diagram illustrating an example of skipping indications, inaccordance with the present disclosure.

FIG. 12 is a diagram illustrating examples of configured grantoccasions, in accordance with the present disclosure.

FIG. 13 is a diagram illustrating an example of a skipping indicationfor multiple grant occasions, in accordance with the present disclosure.

FIG. 14 is a diagram illustrating an example of skipping resources of agrant, in accordance with the present disclosure.

FIG. 15 is a diagram illustrating examples of using uplink controlinformation to indicate skipped resources or non-skipped resources forretransmissions, in accordance with the present disclosure.

FIG. 16 is a diagram illustrating an example process performed, forexample, by a UE, in accordance with the present disclosure.

FIG. 17 is a diagram illustrating an example process performed, forexample, by a network entity, in accordance with the present disclosure.

FIGS. 18-19 are diagrams of example apparatuses for wirelesscommunication, in accordance with the present disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and should not be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. One skilled in theart should appreciate that the scope of the disclosure is intended tocover any aspect of the disclosure disclosed herein, whether implementedindependently of or combined with any other aspect of the disclosure.For example, an apparatus may be implemented or a method may bepracticed using any number of the aspects set forth herein. In addition,the scope of the disclosure is intended to cover such an apparatus ormethod which is practiced using other structure, functionality, orstructure and functionality in addition to or other than the variousaspects of the disclosure set forth herein. It should be understood thatany aspect of the disclosure disclosed herein may be embodied by one ormore elements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, or the like(collectively referred to as “elements”). These elements may beimplemented using hardware, software, or combinations thereof. Whethersuch elements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem.

While aspects may be described herein using terminology commonlyassociated with a 5G or New Radio (NR) radio access technology (RAT),aspects of the present disclosure can be applied to other RATs, such asa 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).

FIG. 1 is a diagram illustrating an example of a wireless network 100,in accordance with the present disclosure. The wireless network 100 maybe or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g.,Long Term Evolution (LTE)) network, among other examples. The wirelessnetwork 100 may include a user equipment (UE) 120 or multiple UEs 120(shown as a UE 120 a, a UE 120 b, a UE 120 c, a UE 120 d, and a UE 120e). The wireless network 100 may also include one or more networkentities, such as base stations 110 (shown as a BS 110 a, a BS 110 b, aBS 110 c, and a BS 110 d), and/or other network entities. A base station110 is a network entity that communicates with UEs 120. A base station110 (sometimes referred to as a BS) may include, for example, an NR basestation, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB(e.g., in 5G), an access point, and/or a transmission reception point(TRP). Each base station 110 may provide communication coverage for aparticular geographic area. In the Third Generation Partnership Project(3GPP), the term “cell” can refer to a coverage area of a base station110 and/or a base station subsystem serving this coverage area,depending on the context in which the term is used.

A base station 110 may provide communication coverage for a macro cell,a pico cell, a femto cell, and/or another type of cell. A macro cell maycover a relatively large geographic area (e.g., several kilometers inradius) and may allow unrestricted access by UEs 120 with servicesubscriptions. A pico cell may cover a relatively small geographic areaand may allow unrestricted access by UEs 120 with service subscription.A femto cell may cover a relatively small geographic area (e.g., a home)and may allow restricted access by UEs 120 having association with thefemto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A basestation 110 for a macro cell may be referred to as a macro base station.A base station 110 for a pico cell may be referred to as a pico basestation. A base station 110 for a femto cell may be referred to as afemto base station or an in-home base station. In the example shown inFIG. 1 , the BS 110 a may be a macro base station for a macro cell 102a, the BS 110 b may be a pico base station for a pico cell 102 b, andthe BS 110 c may be a femto base station for a femto cell 102 c. A basestation may support one or multiple (e.g., three) cells.

In some examples, a cell may not necessarily be stationary, and thegeographic area of the cell may move according to the location of a basestation 110 that is mobile (e.g., a mobile base station). In someexamples, the base stations 110 may be interconnected to one anotherand/or to one or more other base stations 110 or network entities in thewireless network 100 through various types of backhaul interfaces, suchas a direct physical connection or a virtual network, using any suitabletransport network.

In some aspects, the term “base station” (e.g., the base station 110) or“network entity” may refer to an aggregated base station, adisaggregated base station, an integrated access and backhaul (IAB)node, a relay node, and/or one or more components thereof. For example,in some aspects, “base station” or “network entity” may refer to acentral unit (CU), a distributed unit (DU), a radio unit (RU), aNear-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-RealTime (Non-RT) MC, or a combination thereof. In some aspects, the term“base station” or “network entity” may refer to one device configured toperform one or more functions, such as those described herein inconnection with the base station 110. In some aspects, the term “basestation” or “network entity” may refer to a plurality of devicesconfigured to perform the one or more functions. For example, in somedistributed systems, each of a number of different devices (which may belocated in the same geographic location or in different geographiclocations) may be configured to perform at least a portion of afunction, or to duplicate performance of at least a portion of thefunction, and the term “base station” or “network entity” may refer toany one or more of those different devices. In some aspects, the term“base station” or “network entity” may refer to one or more virtual basestations and/or one or more virtual base station functions. For example,in some aspects, two or more base station functions may be instantiatedon a single device. In some aspects, the term “base station” or “networkentity” may refer to one of the base station functions and not another.In this way, a single device may include more than one base station.

The wireless network 100 may include one or more relay stations. A relaystation is a network entity that can receive a transmission of data froman upstream station (e.g., a network entity or a UE 120) and send atransmission of the data to a downstream station (e.g., UE 120 or anetwork entity). A relay station may be a UE 120 that can relaytransmissions for other UEs 120. In the example shown in FIG. 1 , the BS110 d (e.g., a relay base station) may communicate with the BS 110 a(e.g., a macro base station) and the UE 120 d in order to facilitatecommunication between the BS 110 a and the UE 120 d. A base station 110that relays communications may be referred to as a relay station, arelay base station, a relay, or the like.

The wireless network 100 may be a heterogeneous network with networkentities that include different types of BSs, such as macro basestations, pico base stations, femto base stations, relay base stations,or the like. These different types of base stations 110 may havedifferent transmit power levels, different coverage areas, and/ordifferent impacts on interference in the wireless network 100. Forexample, macro base stations may have a high transmit power level (e.g.,5 to 40 watts) whereas pico base stations, femto base stations, andrelay base stations may have lower transmit power levels (e.g., 0.1 to 2watts).

A network controller 130 may couple to or communicate with a set ofnetwork entities and may provide coordination and control for thesenetwork entities. The network controller 130 may communicate with thebase stations 110 via a backhaul communication link. The networkentities may communicate with one another directly or indirectly via awireless or wireline backhaul communication link.

The UEs 120 may be dispersed throughout the wireless network 100, andeach UE 120 may be stationary or mobile. A UE 120 may include, forexample, an access terminal, a terminal, a mobile station, and/or asubscriber unit. A UE 120 may be a cellular phone (e.g., a smart phone),a personal digital assistant (PDA), a wireless modem, a wirelesscommunication device, a handheld device, a laptop computer, a cordlessphone, a wireless local loop (WLL) station, a tablet, a camera, a gamingdevice, a netbook, a smartbook, an ultrabook, a medical device, abiometric device, a wearable device (e.g., a smart watch, smartclothing, smart glasses, a smart wristband, smart jewelry (e.g., a smartring or a smart bracelet)), an entertainment device (e.g., a musicdevice, a video device, and/or a satellite radio), a vehicular componentor sensor, a smart meter/sensor, industrial manufacturing equipment, aglobal positioning system device, and/or any other suitable device thatis configured to communicate via a wireless medium.

Some UEs 120 may be considered machine-type communication (MTC) orevolved or enhanced machine-type communication (eMTC) UEs. An MTC UEand/or an eMTC UE may include, for example, a robot, a drone, a remotedevice, a sensor, a meter, a monitor, and/or a location tag, that maycommunicate with a network entity, another device (e.g., a remotedevice), or some other entity. Some UEs 120 may be consideredInternet-of-Things (IoT) devices, and/or may be implemented as NB-IoT(narrowband IoT) devices. Some UEs 120 may be considered a CustomerPremises Equipment. A UE 120 may be included inside a housing thathouses components of the UE 120, such as processor components and/ormemory components. In some examples, the processor components and thememory components may be coupled together. For example, the processorcomponents (e.g., one or more processors) and the memory components(e.g., a memory) may be operatively coupled, communicatively coupled,electronically coupled, and/or electrically coupled.

In general, any number of wireless networks 100 may be deployed in agiven geographic area. Each wireless network 100 may support aparticular RAT and may operate on one or more frequencies. A RAT may bereferred to as a radio technology, an air interface, or the like. Afrequency may be referred to as a carrier, a frequency channel, or thelike. Each frequency may support a single RAT in a given geographic areain order to avoid interference between wireless networks of differentRATs. In some cases, NR or 5G RAT networks may be deployed.

In some examples, two or more UEs 120 (e.g., shown as UE 120 a and UE120 e) may communicate directly using one or more sidelink channels(e.g., without using a network entity as an intermediary to communicatewith one another). For example, the UEs 120 may communicate usingpeer-to-peer (P2P) communications, device-to-device (D2D)communications, a vehicle-to-everything (V2X) protocol (e.g., which mayinclude a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure(V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or amesh network. In such examples, a UE 120 may perform schedulingoperations, resource selection operations, and/or other operationsdescribed elsewhere herein as being performed by the base station 110.

Devices of the wireless network 100 may communicate using theelectromagnetic spectrum, which may be subdivided by frequency orwavelength into various classes, bands, channels, or the like. Forexample, devices of the wireless network 100 may communicate using oneor more operating bands. In 5G NR, two initial operating bands have beenidentified as frequency range designations FR1 (410 MHz-7.125 GHz) andFR2 (24.25 GHz-52.6 GHz). It should be understood that although aportion of FR1 is greater than 6 GHz, FR1 is often referred to(interchangeably) as a “Sub-6 GHz” band in various documents andarticles. A similar nomenclature issue sometimes occurs with regard toFR2, which is often referred to (interchangeably) as a “millimeter wave”band in documents and articles, despite being different from theextremely high frequency (EHF) band (30 GHz-300 GHz) which is identifiedby the International Telecommunications Union (ITU) as a “millimeterwave” band.

The frequencies between FR1 and FR2 are often referred to as mid-bandfrequencies. Recent 5G NR studies have identified an operating band forthese mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1characteristics and/or FR2 characteristics, and thus may effectivelyextend features of FR1 and/or FR2 into mid-band frequencies. Inaddition, higher frequency bands are currently being explored to extend5G NR operation beyond 52.6 GHz. For example, three higher operatingbands have been identified as frequency range designations FR4a or FR4-1(52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise,it should be understood that the term “sub-6 GHz” or the like, if usedherein, may broadly represent frequencies that may be less than 6 GHz,may be within FR1, or may include mid-band frequencies. Further, unlessspecifically stated otherwise, it should be understood that the term“millimeter wave” or the like, if used herein, may broadly representfrequencies that may include mid-band frequencies, may be within FR2,FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. It iscontemplated that the frequencies included in these operating bands(e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified,and techniques described herein are applicable to those modifiedfrequency ranges.

In some aspects, the UE 120 may include a communication manager 140. Asdescribed in more detail elsewhere herein, the communication manager 140may select first resources to skip in each grant occasion of multiplegrant occasions for communications on a physical uplink channel. Thecommunication manager 140 may transmit uplink control information (UCI)that indicates the first resources or second resources that are not tobe skipped in each grant occasion of the multiple grant occasions. Thecommunication manager 140 may transmit the communications in themultiple grant occasions using the second resources and not the firstresources. Additionally, or alternatively, the communication manager 140may perform one or more other operations described herein.

In some aspects, a network entity (e.g., base station 110) may include acommunication manager 150. As described in more detail elsewhere herein,the communication manager 150 may receive UCI that indicates firstresources or second resources of multiple grant occasions, the firstresources in each grant occasion being first for communications on aphysical uplink channel and the second resources not being skipped. Thecommunication manager 150 may receive the communications in the multiplegrant occasions and decode the communications in the second resourcesand not decoding the communications in the first resources based atleast in part on the UCI. Additionally, or alternatively, thecommunication manager 150 may perform one or more other operationsdescribed herein.

As indicated above, FIG. 1 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 1 .

FIG. 2 is a diagram illustrating an example 200 of a network entity(e.g., base station 110) in communication with a UE 120 in a wirelessnetwork 100, in accordance with the present disclosure. The base station110 may be equipped with a set of antennas 234 a through 234 t, such asT antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a through 252 r, such as R antennas (R≥1).

At the base station 110, a transmit processor 220 may receive data, froma data source 212, intended for the UE 120 (or a set of UEs 120). Thetransmit processor 220 may select one or more modulation and codingschemes (MCSs) for the UE 120 based at least in part on one or morechannel quality indicators (CQIs) received from that UE 120. The basestation 110 may process (e.g., encode and modulate) the data for the UE120 based at least in part on the MCS(s) selected for the UE 120 and mayprovide data symbols for the UE 120. The transmit processor 220 mayprocess system information (e.g., for semi-static resource partitioninginformation (SRPI)) and control information (e.g., CQI requests, grants,and/or upper layer signaling) and provide overhead symbols and controlsymbols. The transmit processor 220 may generate reference symbols forreference signals (e.g., a cell-specific reference signal (CRS) or ademodulation reference signal (DMRS)) and synchronization signals (e.g.,a primary synchronization signal (PSS) or a secondary synchronizationsignal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO)processor 230 may perform spatial processing (e.g., precoding) on thedata symbols, the control symbols, the overhead symbols, and/or thereference symbols, if applicable, and may provide a set of output symbolstreams (e.g., T output symbol streams) to a corresponding set of modems232 (e.g., T modems), shown as modems 232 a through 232 t. For example,each output symbol stream may be provided to a modulator component(shown as MOD) of a modem 232. Each modem 232 may use a respectivemodulator component to process a respective output symbol stream (e.g.,for OFDM) to obtain an output sample stream. Each modem 232 may furtheruse a respective modulator component to process (e.g., convert toanalog, amplify, filter, and/or upconvert) the output sample stream toobtain a downlink signal. The modems 232 a through 232 t may transmit aset of downlink signals (e.g., T downlink signals) via a correspondingset of antennas 234 (e.g., T antennas), shown as antennas 234 a through234 t.

At the UE 120, a set of antennas 252 (shown as antennas 252 a through252 r) may receive the downlink signals from the base station 110 and/orother base stations 110 and may provide a set of received signals (e.g.,R received signals) to a set of modems 254 (e.g., R modems), shown asmodems 254 a through 254 r. For example, each received signal may beprovided to a demodulator component (shown as DEMOD) of a modem 254.Each modem 254 may use a respective demodulator component to condition(e.g., filter, amplify, downconvert, and/or digitize) a received signalto obtain input samples. Each modem 254 may use a demodulator componentto further process the input samples (e.g., for OFDM) to obtain receivedsymbols. A MIMO detector 256 may obtain received symbols from the modems254, may perform MIMO detection on the received symbols if applicable,and may provide detected symbols. A receive processor 258 may process(e.g., demodulate and decode) the detected symbols, may provide decodeddata for the UE 120 to a data sink 260, and may provide decoded controlinformation and system information to a controller/processor 280. Theterm “controller/processor” may refer to one or more controllers, one ormore processors, or a combination thereof. A channel processor maydetermine a reference signal received power (RSRP) parameter, a receivedsignal strength indicator (RSSI) parameter, a reference signal receivedquality (RSRQ) parameter, and/or a CQI parameter, among other examples.In some examples, one or more components of the UE 120 may be includedin a housing 284.

The network controller 130 may include a communication unit 294, acontroller/processor 290, and a memory 292. The network controller 130may include, for example, one or more devices in a core network. Thenetwork controller 130 may communicate with the network entity via thecommunication unit 294.

One or more antennas (e.g., antennas 234 a through 234 t and/or antennas252 a through 252 r) may include, or may be included within, one or moreantenna panels, one or more antenna groups, one or more sets of antennaelements, and/or one or more antenna arrays, among other examples. Anantenna panel, an antenna group, a set of antenna elements, and/or anantenna array may include one or more antenna elements (within a singlehousing or multiple housings), a set of coplanar antenna elements, a setof non-coplanar antenna elements, and/or one or more antenna elementscoupled to one or more transmission and/or reception components, such asone or more components of FIG. 2 .

On the uplink, at the UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (e.g., forreports that include RSRP, RSSI, RSRQ, and/or CQI) from thecontroller/processor 280. The transmit processor 264 may generatereference symbols for one or more reference signals. The symbols fromthe transmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by the modems 254 (e.g., for DFT-s-OFDM orCP-OFDM), and transmitted to the network entity. In some examples, themodem 254 of the UE 120 may include a modulator and a demodulator. Insome examples, the UE 120 includes a transceiver. The transceiver mayinclude any combination of the antenna(s) 252, the modem(s) 254, theMIMO detector 256, the receive processor 258, the transmit processor264, and/or the TX MIMO processor 266. The transceiver may be used by aprocessor (e.g., the controller/processor 280) and the memory 282 toperform aspects of any of the methods described herein (e.g., withreference to FIGS. 4-19 ).

At the network entity (e.g., base station 110), the uplink signals fromUE 120 and/or other UEs may be received by the antennas 234, processedby the modem 232 (e.g., a demodulator component, shown as DEMOD, of themodem 232), detected by a MIMO detector 236 if applicable, and furtherprocessed by a receive processor 238 to obtain decoded data and controlinformation sent by the UE 120. The receive processor 238 may providethe decoded data to a data sink 239 and provide the decoded controlinformation to the controller/processor 240. The network entity mayinclude a communication unit 244 and may communicate with the networkcontroller 130 via the communication unit 244. The network entity mayinclude a scheduler 246 to schedule one or more UEs 120 for downlinkand/or uplink communications. In some examples, the modem 232 of thenetwork entity may include a modulator and a demodulator. In someexamples, the network entity includes a transceiver. The transceiver mayinclude any combination of the antenna(s) 234, the modem(s) 232, theMIMO detector 236, the receive processor 238, the transmit processor220, and/or the TX MIMO processor 230. The transceiver may be used by aprocessor (e.g., the controller/processor 240) and the memory 242 toperform aspects of any of the methods described herein (e.g., withreference to FIGS. 4-19 ).

A controller/processor of a network entity, (e.g., thecontroller/processor 240 of the base station 110), thecontroller/processor 280 of the UE 120, and/or any other component(s) ofFIG. 2 may perform one or more techniques associated with indicating,with a single UCI, resources to skip for multiple grant occasions, asdescribed in more detail elsewhere herein. For example, thecontroller/processor 240 of the base station 110, thecontroller/processor 280 of the UE 120, and/or any other component(s) ofFIG. 2 may perform or direct operations of, for example, process 1600 ofFIG. 16 , process 1700 of FIG. 17 , and/or other processes as describedherein. The memory 242 and the memory 282 may store data and programcodes for the network entity and the UE 120, respectively. In someexamples, the memory 242 and/or the memory 282 may include anon-transitory computer-readable medium storing one or more instructions(e.g., code and/or program code) for wireless communication. Forexample, the one or more instructions, when executed (e.g., directly, orafter compiling, converting, and/or interpreting) by one or moreprocessors of the network entity and/or the UE 120, may cause the one ormore processors, the UE 120, and/or the network entity to perform ordirect operations of, for example, process 1600 of FIG. 16 , process1700 of FIG. 17 , and/or other processes as described herein. In someexamples, executing instructions may include running the instructions,converting the instructions, compiling the instructions, and/orinterpreting the instructions, among other examples.

In some aspects, the UE 120 includes means for selecting first resourcesto skip in each grant occasion of multiple grant occasions forcommunications on a physical uplink channel; means for transmitting UCIthat indicates the first resources or second resources that are not tobe skipped in each grant occasion of the multiple grant occasions;and/or means for transmitting the communications in the multiple grantoccasions using the second resources and not the first resources. Themeans for the UE 120 to perform operations described herein may include,for example, one or more of communication manager 140, antenna 252,modem 254, MIMO detector 256, receive processor 258, transmit processor264, TX MIMO processor 266, controller/processor 280, or memory 282.

In some aspects, a network entity (e.g., base station 110) includesmeans for receiving UCI that indicates first resources or secondresources of multiple grant occasions, the first resources in each grantoccasion being first for communications on a physical uplink channel andthe second resources not being skipped; means for receiving thecommunications in the multiple grant occasions; and/or means fordecoding the communications in the second resources and not decoding thecommunications in the first resources based at least in part on the UCI.In some aspects, the means for the network entity to perform operationsdescribed herein may include, for example, one or more of communicationmanager 150, transmit processor 220, TX MIMO processor 230, modem 232,antenna 234, MIMO detector 236, receive processor 238,controller/processor 240, memory 242, or scheduler 246.

While blocks in FIG. 2 are illustrated as distinct components, thefunctions described above with respect to the blocks may be implementedin a single hardware, software, or combination component or in variouscombinations of components. For example, the functions described withrespect to the transmit processor 264, the receive processor 258, and/orthe TX MIMO processor 266 may be performed by or under the control ofthe controller/processor 280.

As indicated above, FIG. 2 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 2 .

FIG. 3 is a diagram illustrating an example of a disaggregated basestation 300, in accordance with the present disclosure.

Deployment of communication systems, such as 5G NR systems, may bearranged in multiple manners with various components or constituentparts. In a 5G NR system, or network, a network node, a network entity,a mobility element of a network, a radio access network (RAN) node, acore network node, a network element, or a network equipment, such as abase station, or one or more units (or one or more components)performing base station functionality, may be implemented in anaggregated or disaggregated architecture. For example, a BS (such as aNode B, evolved NB (eNB), NR BS, 5G NB, access point (AP), a TRP, or acell, etc.) may be implemented as an aggregated base station (also knownas a standalone BS or a monolithic BS) or a disaggregated base station.

An aggregated base station may be configured to utilize a radio protocolstack that is physically or logically integrated within a single RANnode. A disaggregated base station may be configured to utilize aprotocol stack that is physically or logically distributed among two ormore units (such as one or more CUs, one or more DUs, or one or moreRUs). In some aspects, a CU may be implemented within a RAN node, andone or more DUs may be co-located with the CU, or alternatively, may begeographically or virtually distributed throughout one or multiple otherRAN nodes. The DUs may be implemented to communicate with one or moreRUs. Each of the CU, DU and RU also can be implemented as virtual units(e.g., a virtual central unit (VCU), a virtual distributed unit (VDU),or a virtual radio unit (VRU)).

Base station-type operation or network design may consider aggregationcharacteristics of base station functionality. For example,disaggregated base stations may be utilized in an IAB network, an openradio access network (O-RAN (such as the network configuration sponsoredby the O-RAN Alliance)), or a virtualized radio access network (vRAN,also known as a cloud radio access network (C-RAN)).

Disaggregation may include distributing functionality across two or moreunits at various physical locations, as well as distributingfunctionality for at least one unit virtually, which can enableflexibility in network design. The various units of the disaggregatedbase station, or disaggregated RAN architecture, can be configured forwired or wireless communication with at least one other unit.

The disaggregated base station 300 architecture may include one or moreCUs 310 that can communicate directly with a core network 320 via abackhaul link, or indirectly with the core network 320 through one ormore disaggregated base station units (such as a Near-RT RIC 325 via anE2 link, or a Non-RT RIC 315 associated with a Service Management andOrchestration (SMO) Framework 305, or both). A CU 310 may communicatewith one or more DUs 330 via respective midhaul links, such as an F1interface. The DUs 330 may communicate with one or more RUs 340 viarespective fronthaul links. The fronthaul link, the midhaul link, andthe backhaul link may be generally referred to as “communication links.”The RUs 340 may communicate with respective UEs 120 via one or more RFaccess links. In some aspects, the UE 120 may be simultaneously servedby multiple RUs 340. The DUs 330 and the RUs 340 may also be referred toas “O-RAN DUs (O-DUs”) and “O-RAN RUs (O-RUs)”, respectively. A networkentity may include a CU, a DU, an RU, or any combination of CUs, DUs,and RUs. A network entity may include a disaggregated base station orone or more components of the disaggregated base station, such as a CU,a DU, an RU, or any combination of CUs, DUs, and RUs. A network entitymay also include one or more of a TRP, a relay station, a passivedevice, an intelligent reflective surface (IRS), or other componentsthat may provide a network interface for or serve a UE, mobile station,sensor/actuator, or other wireless device.

Each of the units (e.g., the CUs 310, the DUs 330, the RUs 340, as wellas the Near-RT RICs 325, the Non-RT RICs 315 and the SMO Framework 305)may include one or more interfaces or be coupled to one or moreinterfaces configured to receive or transmit signals, data, orinformation (collectively, signals) via a wired or wireless transmissionmedium. Each of the units, or an associated processor or controllerproviding instructions to the communication interfaces of the units, canbe configured to communicate with one or more of the other units via thetransmission medium. For example, the units can include a wiredinterface configured to receive or transmit signals over a wiredtransmission medium to one or more of the other units. Additionally, theunits can include a wireless interface, which may include a receiver, atransmitter or transceiver (such as an RF transceiver), configured toreceive or transmit signals, or both, over a wireless transmissionmedium to one or more of the other units.

In some aspects, the CU 310 may host one or more higher layer controlfunctions. Such control functions can include radio resource control(RRC), packet data convergence protocol (PDCP), service data adaptationprotocol (SDAP), or the like. Each control function can be implementedwith an interface configured to communicate signals with other controlfunctions hosted by the CU 310. The CU 310 may be configured to handleuser plane functionality (i.e., Central Unit—User Plane (CU-UP)),control plane functionality (i.e., Central Unit—Control Plane (CU-CP)),or a combination thereof. In some implementations, the CU 310 can belogically split into one or more CU-UP units and one or more CU-CPunits. The CU-UP unit can communicate bidirectionally with the CU-CPunit via an interface, such as the E1 interface when implemented in anO-RAN configuration. The CU 310 can be implemented to communicate withthe DU 330, as necessary, for network control and signaling.

The DU 330 may correspond to a logical unit that includes one or morebase station functions to control the operation of one or more RUs 340.In some aspects, the DU 330 may host one or more of a radio link control(RLC) layer, a medium access control (MAC) layer, and one or more highphysical (PHY) layers (such as modules for forward error correction(FEC) encoding and decoding, scrambling, modulation and demodulation, orthe like) depending, at least in part, on a functional split, such asthose defined by the 3GPP. In some aspects, the DU 330 may further hostone or more low PHY layers. Each layer (or module) can be implementedwith an interface configured to communicate signals with other layers(and modules) hosted by the DU 330, or with the control functions hostedby the CU 310.

Lower-layer functionality can be implemented by one or more RUs 340. Insome deployments, an RU 340, controlled by a DU 330, may correspond to alogical node that hosts RF processing functions, or low-PHY layerfunctions (such as performing fast Fourier transform (FFT), inverse FFT(iFFT), digital beamforming, physical random access channel (PRACH)extraction and filtering, or the like), or both, based at least in parton the functional split, such as a lower layer functional split. In suchan architecture, the RU(s) 340 can be implemented to handle over the air(OTA) communication with one or more UEs 120. In some implementations,real-time and non-real-time aspects of control and user planecommunication with the RU(s) 340 can be controlled by the correspondingDU 330. In some scenarios, this configuration can enable the DU(s) 330and the CU 310 to be implemented in a cloud-based RAN architecture, suchas a vRAN architecture.

The SMO Framework 305 may be configured to support RAN deployment andprovisioning of non-virtualized and virtualized network elements. Fornon-virtualized network elements, the SMO Framework 305 may beconfigured to support the deployment of dedicated physical resources forRAN coverage requirements which may be managed via an operations andmaintenance interface (such as an O1 interface). For virtualized networkelements, the SMO Framework 305 may be configured to interact with acloud computing platform (such as an open cloud (O-Cloud) 390) toperform network element life cycle management (such as to instantiatevirtualized network elements) via a cloud computing platform interface(such as an O2 interface). Such virtualized network elements caninclude, but are not limited to, CUs 310, DUs 330, RUs 340 and Near-RTRICs 325. In some implementations, the SMO Framework 305 can communicatewith a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, viaan O1 interface. Additionally, in some implementations, the SMOFramework 305 can communicate directly with one or more RUs 340 via anO1 interface. The SMO Framework 305 also may include a Non-RT RIC 315configured to support functionality of the SMO Framework 305.

The Non-RT RIC 315 may be configured to include a logical function thatenables non-real-time control and optimization of RAN elements andresources, Artificial Intelligence/Machine Learning (AI/ML) workflowsincluding model training and updates, or policy-based guidance ofapplications/features in the Near-RT RIC 325. The Non-RT RIC 315 may becoupled to or communicate with (such as via an A1 interface) the Near-RTRIC 325. The Near-RT RIC 325 may be configured to include a logicalfunction that enables near-real-time control and optimization of RANelements and resources via data collection and actions over an interface(such as via an E2 interface) connecting one or more CUs 310, one ormore DUs 330, or both, as well as an with the Near-RT RIC 325.

In some implementations, to generate AI/ML models to be deployed in theNear-RT RIC 325, the Non-RT MC 315 may receive parameters or externalenrichment information from external servers. Such information may beutilized by the Near-RT MC 325 and may be received at the SMO Framework305 or the Non-RT MC 315 from non-network data sources or from networkfunctions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325may be configured to tune RAN behavior or performance. For example, theNon-RT RIC 315 may monitor long-term trends and patterns for performanceand employ AI/ML models to perform corrective actions through the SMOFramework 305 (such as reconfiguration via O1) or via creation of RANmanagement policies (such as A1 policies).

As indicated above, FIG. 3 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 3 .

FIG. 4 is a diagram illustrating an example 400 of a slot format, inaccordance with the present disclosure. As shown in FIG. 4 ,time-frequency resources in a radio access network may be partitionedinto resource blocks, shown by a single resource block (RB) 405. An RB405 is sometimes referred to as a physical resource block (PRB). An RB405 includes a set of subcarriers (e.g., 12 subcarriers) and a set ofsymbols (e.g., 14 symbols) that are schedulable by a network entity(e.g., base station 110) as a unit. In some aspects, an RB 405 mayinclude a set of subcarriers in a single slot. As shown, a singletime-frequency resource included in an RB 405 may be referred to as aresource element (RE) 410. An RE 410 may include a single subcarrier(e.g., in frequency) and a single symbol (e.g., in time). A symbol maybe referred to as an orthogonal frequency division multiplexing (OFDM)symbol. An RE 410 may be used to transmit one modulated symbol, whichmay be a real value or a complex value.

In some telecommunication systems (e.g., NR), RBs 405 may span 12subcarriers with a subcarrier spacing of, for example, 15 kilohertz(kHz), 30 kHz, 60 kHz, or 120 kHz, among other examples, over a 0.1millisecond (ms) duration. A radio frame may include 40 slots and mayhave a length of 10 ms. Consequently, each slot may have a length of0.25 ms. However, a slot length may vary depending on a numerology usedto communicate (e.g., a subcarrier spacing and/or a cyclic prefixformat). A slot may be configured with a link direction (e.g., downlinkor uplink) for transmission. In some aspects, the link direction for aslot may be dynamically configured.

As indicated above, FIG. 4 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 4 .

FIG. 5 is a diagram illustrating an example 500 of uplink configuredgrant (CG) communication, in accordance with the present disclosure.

In some aspects, PRBs for uplink communications may be granteddynamically, such as with a scheduling request (SR) or a buffer statusreport (BSR). A UE may first transmit an SR on a physical uplink controlchannel (PUCCH), requesting radio resources in the uplink when the UEhas pending data in its buffer. With periodic BSR reporting, the networkentity knows the available buffer at the UE. The network entity thentransmits an uplink grant downlink control information (DCI). Theallocated resources are specified in the DCI for the UE to transmit acommunication on the physical uplink shared channel (PUSCH).

Alternatively, PRBs for uplink communications may be granted accordingto a configuration. For example, CG communications may include periodicuplink communications that are configured for a UE, such that thenetwork entity does not need to send separate DCI to schedule eachuplink communication, thereby conserving signaling overhead.

As shown in example 500, a UE (e.g., UE 120) may be configured with a CGconfiguration for CG communications. For example, the UE may receive theCG configuration via an RRC message transmitted by a network entity(e.g., a base station 110). The CG configuration may indicate a resourceallocation associated with CG uplink communications (e.g., in a timedomain, frequency domain, spatial domain, and/or code domain) and aperiodicity at which the resource allocation is repeated, resulting inperiodically reoccurring scheduled CG occasions 505 for the UE. In someexamples, the CG configuration may identify a resource pool or multipleresource pools that are available to the UE for an uplink transmission.The CG configuration may configure contention-free CG communications(e.g., where resources are dedicated for the UE to transmit uplinkcommunications) or contention-based CG communications (e.g., where theUE contends for access to a channel in the configured resourceallocation, such as by using a channel access procedure or a channelsensing procedure).

The network entity may transmit CG activation DCI to the UE to activatethe CG configuration for the UE. The network entity may indicate, in theCG activation DCI, communication parameters, such as an MCS, an RBallocation, and/or antenna ports, for the CG PUSCH communications to betransmitted in the scheduled CG occasions 505. The UE may begintransmitting in the CG occasions 505 based at least in part on receivingthe CG activation DCI. For example, beginning with a next scheduled CGoccasion 505 subsequent to receiving the CG activation DCI, the UE maytransmit a PUSCH communication in the scheduled CG occasions 505 usingthe communication parameters indicated in the CG activation DCI. The UEmay refrain from transmitting in configured CG occasions 505 prior toreceiving the CG activation DCI.

The network entity may transmit CG reactivation DCI to the UE to changethe communication parameters for the CG PUSCH communications. Based atleast in part on receiving the CG reactivation DCI, and the UE may begintransmitting in the scheduled CG occasions 505 using the communicationparameters indicated in the CG reactivation DCI. For example, beginningwith a next scheduled CG occasion 505 subsequent to receiving the CGreactivation DCI, the UE may transmit PUSCH communications in thescheduled CG occasions 505 based at least in part on the communicationparameters indicated in the CG reactivation DCI.

In some cases, such as when the network entity needs to override ascheduled CG communication for a higher priority communication, thenetwork entity may transmit CG cancellation DCI to the UE to temporarilycancel or deactivate one or more subsequent CG occasions 505 for the UE.The CG cancellation DCI may deactivate only a subsequent one CG occasion505 or a subsequent N CG occasions 505 (where N is an integer). CGoccasions 505 after the one or more (e.g., N) CG occasions 505subsequent to the CG cancellation DCI may remain activated. Based atleast in part on receiving the CG cancellation DCI, the UE may refrainfrom transmitting in the one or more (e.g., N) CG occasions 505subsequent to receiving the CG cancellation DCI. As shown in example500, the CG cancellation DCI cancels one subsequent CG occasion 505 forthe UE. After the CG occasion 505 (or N CG occasions) subsequent toreceiving the CG cancellation DCI, the UE may automatically resumetransmission in the scheduled CG occasions 505.

The network entity may transmit CG release DCI to the UE to deactivatethe CG configuration for the UE. The UE may stop transmitting in thescheduled CG occasions 505 based at least in part on receiving the CGrelease DCI. For example, the UE may refrain from transmitting in anyscheduled CG occasions 505 until another CG activation DCI is receivedfrom the base station. Whereas the CG cancellation DCI may deactivateonly a subsequent one CG occasion 505 or a subsequent N CG occasions505, the CG release DCI deactivates all subsequent CG occasions 505 fora given CG configuration for the UE until the given CG configuration isactivated again by a new CG activation DCI.

With dynamic grants, RB allocation in the uplink may match theinformation bits of a communication and thus use less power. However,transmitting an SR and waiting for an uplink grant increases latency.With CG, RB allocation might be more than what is needed for the UEinformation bits, and more power may be consumed than necessary. The UEwill have to pad the information bits such that all the allocatedresources to the UE are used. If the UE has no information bits, (nopacket convergence data protocol PDCP packets pending) or fewerinformation bits, the UE may still be required to transmit over theallocation resources.

As indicated above, FIG. 5 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 5 .

FIG. 6 is a diagram illustrating an example 600 of skipping acommunication associated with a grant, in accordance with the presentdisclosure.

With CG scheduling, resource allocation may be large, resourceutilization may be high, interference in the uplink may increase, andpower consumption may be higher. The higher power consumption mayincrease the thermal properties of the UE, which may be an importantissue for extended reality (XR) devices or augmented reality (AR)devices.

In some aspects, a UE may skip or ignore a communication associated witha grant, whether a dynamic grant or a CG. Otherwise, the UE transmitspadded bits over the allocated resources (e.g., RBs), even though theinformation bits may not require the allocated number of RBs fortransmission. The allocated number of RBs may be an overallocation.

Example 600 shows that a UE may skip a communication associated with agrant. As shown by reference number 605, the UE may receive aconfiguration (e.g., via RRC) that configures the UE to be able to skipa communication associated with a grant. As shown by reference number610, the UE may receive the grant for an uplink communication. As shownby reference number 615, the UE may transmit the uplink communication(e.g., MAC protocol data unit (PDU)) if data is available. Powerconsumption may increase if the grant is larger. If no data isavailable, the UE may not transmit the uplink communication. However,latency may increase if there are a few bits that need to betransmitted, because the bits may be transmitted in a later MAC PDU.

As indicated above, FIG. 6 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 6 .

FIG. 7 is a diagram illustrating an example 700 of skipping resources ofa grant, in accordance with the present disclosure.

In some aspects, a UE may skip resources of a grant rather than skippingthe grant altogether. Example 700 shows resources of a grant for a MACPDU that include skipped resources 702 (resources that will be skipped)and non-skipped resources 704 (resources that will not be skipped). Thisflexible uplink skipping may enable the UE to select a subset ofresources of the grant (and in effect select a subset of the resourcesof the grant to skip) based at least in part on a size of the payload.As a result, the UE conserves power by not transmitting over all of theresources of the grant. In some aspects, the UE may provide a skippingindication that indicates that the UE is skipping resources of the grantand/or using only a subset (e.g., a non-zero proper subset) of resourcesof the grant. The skipping indication may indicate the skipped resourcesand/or the non-skipped resources.

Example 700 shows a UE that may transmit over a subset of grantedresources. As shown by reference number 705, the UE may receive aconfiguration for flexible uplink skipping (e.g., via RRC signaling). Asshown by reference number 710, the UE may receive an uplink grant for acommunication (e.g., new uplink transmission). The grant may include anumber of allocated RBs (total amount of RBs). As shown by referencenumber 715, if data is available, the UE may determine if an amount ofdata in the buffer satisfies a data threshold. For example, as shown byreference number 720, if a number of bits in the buffer requires lessthan the total amount of RBs, the UE may transmit over a subset of thetotal quantity of RBs. If the amount of data to be transmitted does notrequires less than the total quantity of RBs, the UE may transmit thedata over the total quantity of RBs (using all of the RBs). By using asubset of the total quantity of RBs rather than no RBs or all of theRBs, the UE may reduce power consumption, conserve signaling resources,and reduce delay.

In some aspects, the UE may transmit UCI 722 that includes a skippingindication that informs the network entity of the skipped resources 702and that the network entity may decode only the non-skipped resources704 for an uplink MAC PDU. The UCI may a flexible uplink skipping (FUS)UCI, or a UCI-FUS. The UCI-FUS may indicate which resources have beenskipped, such as a quantity of RBs that are skipped or an indication oftime and frequency resources that are skipped (e.g., slot numbers,symbol numbers, RB numbers, and/or RB group numbers). The UCI-FUS mayalternatively indicate which resources have not been skipped, and thenetwork entity may determine the skipped resources 702 from theindication of the non-skipped resources 704. The UCI-FUS may betransmitted on the PUCCH, which may be on the same slot as a PUSCHcommunication or on different slots. That is, the UCI-FUS may be used toadapt the transport block (TB) size.

As indicated above, FIG. 7 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 7 .

FIG. 8 is a diagram illustrating an example 800 of a skippingindication, in accordance with the present disclosure.

Example 800 shows a skipping indication in UCI that indicates resourcesthat are skipped as part of uplink flexible skipping, or a UCI-FUS. Theskipped resources may be in the frequency domain and/or the time domain.The skipping indication may indicate, for example, for slot 0, symbols10-13 are skipped, and PRBs greater than a specified PRB number areskipped. The skipping indication may specify one or more time-frequencysets of resources from among multiple time-frequency sets of resources(e.g., sets of PRBs, sets of symbols). The multiple time-frequency setsmay be specified via RRC signaling.

In an example, if there are 14 bits available for the UCI, Set 0 mayhave 14 most significant bits (MSBs) that indicate a skipping indicationacross 14 symbols. A bit with a value of 1 may indicate that a symbol isskipped. A bit with a value of 0 may indicate that a symbol is notskipped (all RBs are used). Set 1 may have 14 MSBs that indicate whetherthe group of RBs in a bandwidth part (BWP) are skipped. The BWP may bedivided into 14 RB groups (RBGs), and the 14 MSBs may indicate resourcesthat are skipped over the RBGs. Set 2 may have a finer granularity fortime and frequency (and require more bits). Other set definitions thatmay be used include a set having a pair of bits that indicate both timeand frequency skipping. In some aspects, the skipping indication mayindicate a TB size for the uplink to help quantify the amount ofresources that are needed.

As indicated above, FIG. 8 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 8 .

FIG. 9 is a diagram illustrating an example 900 of skipping indications,in accordance with the present disclosure. Example 900 shows REs thatare used for PUSCH communications, a DMRS, or a phase tracking referencesignal (PTRS).

Example 900 shows an example of skipping RBs of a grant but using allsymbols of the grant. Example 900 shows that the network entity mayreserve some PUSCH REs as a skipping indication in an RB. The skippingindication in the REs may include a type of modulation (e.g., MCS), azero power, or a specified reference signal. A set of REs may bereserved for the skipping indication. The REs may be configurable viaRRC signaling. The skipping indication may include a resource identifier(ID), and a skipping pattern that indicates skipped or used RBs(subcarrier locations) and/or symbols (symbol locations). An RRCconfiguration may include a pattern type or a location of an RE. SomeREs may be unused.

As indicated above, FIG. 9 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 9 .

FIG. 10 is a diagram illustrating an example 1000 of skippingindications, in accordance with the present disclosure.

Example 1000 shows an example of skipping RBs of a grant but using allsymbols of the grant. Example 1000 shows that the network entity mayreserve some PUSCH REs as a skipping indication in an RB. The REs may befront-loaded to reduce latency. The components of a PUSCH communicationmay be based on the quantity of symbols that are used. The skippingindication may indicate RBs (negative skipping) and/or symbols (positiveskipping) in each RB.

If an RB is not skipped, the network entity continues to check forreserved REs for a skipping indication in the time domain. If an RB isskipped, the network entity may not continue to check REs for a skippingindication in the time domain. The network entity may determine thatsymbols past the skipping indication are not used or used, depending onthe information in the REs.

As indicated above, FIG. 10 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 10 .

FIG. 11 is a diagram illustrating an example 1100 of skippingindications, in accordance with the present disclosure.

In some aspects, to ease blind detection at the network entity, thenetwork entity may limit the UE's freedom in selecting resources toskip. While the network entity may allow the UE to skip some resourcesin the uplink, the network entity may guide the UE skipping mechanism.The network entity may configure, via RRC signaling, a starting PRBwhere the UE is to transmit when implementing flexible uplink skipping.The network entity may also RRC configure the flexible uplink skippingwith an RB comb pattern. Example 1100 shows an example of a combpattern. The comb pattern may have an RB comb offset. Example 1100 showsan RB comb offset of 4 in example 1100 (there are 3 skipped RBs beforetransmission at a 4^(th) RB offset). The comb pattern may also have anRE comb offset, which indicates where the skipped RB starts. The combpattern may limit the quantity of symbols that are skipped.

In some aspects, when the UE transmits over a subset of RBs, the DMRSmay be present in the allocated RBs. The UE may first perform coherentenergy detection on the DMRS positions. According to the information ofthe time-frequency location where the DMRS is detected, any strongsignal detected by the network entity on the DMRS configured resourcesis considered to be a valid DMRS in a used RB. An energy detectionthreshold may be maintained by the network entity, and a separate energydetection threshold can be defined for single user MIMO (SU-MIMO) ormulti-user MIMO

In some aspects, a power level of the subset of resources may be higherthan a power level of another set of resources. RBs that contain uplinkcommunications may be at power levels higher than unused RBs. Thenetwork entity may maintain a power level threshold to determine thepower level of the unused subset of resources is higher than a powerlevel of a used subset of resources.

As indicated above, FIG. 11 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 11 .

FIG. 12 is a diagram illustrating examples 1200 and 1202 of configuredgrant occasions, in accordance with the present disclosure.

One or more grant configurations may be activated, and each grantconfiguration may specify multiple grant occasions, such as multiple CGoccasions for CG. Alternatively, CG occasions may belong to the samelegacy semi-static configuration. In addition to CG transmissions for aTB, K retransmissions may be configured for the TB (via RRC signaling)to improve transmission reliability. Example 1200 shows multiple CGoccasions for transmissions and for retransmissions, which may beconfigured with a periodicity and an offset.

Example 1202 shows there may be flexible uplink skipping for multiplegrant occasions, whether for CG, PUSCH grants, or dynamic grants. The UEmay transmit a UCI-FUS before each CG occasion that has skippedresources. However, there may be multiple UCI-FUSs that consumesignaling overhead.

As indicated above, FIG. 12 provides some examples. Other examples maydiffer from what is described with regard to FIG. 12 .

FIG. 13 is a diagram illustrating an example 1300 of a skippingindication for multiple grant occasions, in accordance with the presentdisclosure.

According to various aspects described herein, a UE may select skippedresources (first resources to be skipped) in each grant occasion ofmultiple grant occasions to skip for communications on a physical uplinkchannel and transmit a single UCI (e.g., UCI-FUS) that indicates theskipped resources of the multiple grant occasions. The single UCI mayalso indicate non-skipped resources (second resources that are not to beskipped) such that the network entity derives the skipped resources fromthe non-skipped resources. That is, the single UCI may effectivelyindicate the skipped resources when indicating the non-skippedresources. The multiple grant occasions may belong to a single grantconfiguration (e.g., semi-static CG activated by DCI, grant for PUSCHtransmissions) or to multiple grant configurations.

Example 1300 shows a single UCI-FUS 1302 that indicates a skippingpattern 1304 that applies to multiple grant occasions, such as CGoccasion 1306 and CG occasion 1308. The UCI-FUS 1302 may be transmittedover PUCCH resources that are configured by a network entity. This mayenable the network entity to control how often the UCI-FUS istransmitted. If additional data arrives and the skipping indication isno longer valid, the UE may transmit a new UCI-FUS to reconfigure theskipping over the remaining CG occasions. For example, the UE may selecta different skipping pattern 1310 that is indicated with a singleUCI-FUS 1312 that applies to CG occasion 1314 and CG occasion 1316.

In some aspects, the UE may indicate a skipping pattern (e.g., patternover symbols and RBs) using a bitmap (e.g., bits indicating time and/orfrequency resources). The UE may also receive an RRC configuration ofthe skipping pattern and indicate an index corresponding to the skippingpattern, instead of a bitmap, to reduce overhead. That is, the UCI-FUSmay carry just an index that corresponds to a skipping pattern in agrant occasion for which the actual skipping configuration is RRCconfigured.

As indicated above, FIG. 13 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 13 .

FIG. 14 is a diagram illustrating an example 1400 of skipping resourcesof a grant, in accordance with the present disclosure. As shown in FIG.14 , a network entity 1410 (e.g., base station 110) and a UE 1420 (e.g.,UE 120) may communicate with one another via a wireless network (e.g.,wireless network 100).

As shown by reference number 1425, the UE 1420 may select skippedresources to skip in each grant occasion of multiple grant occasions forcommunications on a physical uplink channel (e.g., PUCCH, PUSCH). Asshown by reference number 1430, the UE 1420 may transmit an indication(e.g., UCI-FUS) that indicates the skipped resources of the multiplegrant occasions. The UE 1420 may alternatively indicate non-skippedresources such that the skipped resources can be derived. As shown byreference number 1435, the UE 1420 may transmit the communications inthe multiple grant occasions using the non-skipped resources and not theskipped resources.

As shown by reference number 1440, the network entity 1410 decode thecommunications in the non-skipped resources and not in the skippedresources. As a result, the network entity 1410 and the UE 1420 conserveprocessing resources, signaling resources, and power. By using a singleUCI for multiple grant occasions rather than UCI for each grantoccasion, the network entity 1410 and the UE 1420 conserve additionalprocessing resources and signaling resources.

In some aspects, the UE 1420 may indicate a skipping pattern forretransmission, such as for K retransmissions. As shown by referencenumber 1445, the UE 1420 may transmit UCI that indicates skippedresources or non-skipped resources for K retransmissions in multiplegrant occasions. The UCI may be a UCI-FUS that indicates a skippingpattern. As shown by reference number 1450, the UE 1420 may transmit theretransmissions in the multiple grant occasions using the non-skippedresources and not using the skipped resources. The skipping pattern mayexplicitly indicate the skipped resources and/or the non-skippedresources.

In some aspects, the UE 1420 may transmit a cancellation indication, asshown by reference number 1455, which may be included in UCI. The UE1420 may not transmit a new UCI-FUS after the cancellation indication,and the UE 1420 may continue to use all resources in the grant occasionswithout skipping resources.

As indicated above, FIG. 14 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 14 .

FIG. 15 is a diagram illustrating examples 1500 and 1502 of using UCI toindicate skipped resources or non-skipped resources for retransmissions,in accordance with the present disclosure.

The skipping pattern used for retransmissions may be indicated by a timeand frequency bitmap in the UCI-FUS. This allows for maximum flexibilityand allows the UE 1420 to transmit over different sets of resources. Forexample, a bitmap in the UCI-FUS for each CG occasion of theretransmissions may include or be indicated by 14 MSBs that indicate askipping pattern over 14 symbols. In another example, the MSBs mayindicate whether RBs or a RBGs in a BWP are skipped. More bits may beused to indicate a bitmap with finer time and frequency granularity. Insome aspects, the network entity 1410 may use RRC signaling to configureskipping patterns, and the network entity 1410 may use an index for askipping pattern, instead of a bitmap, to reduce overhead of theUCI-FUS. In this way, the UCI-FUS may include an index for a skippingpattern rather than using more information to detail the skippingpattern.

Different skipping patterns may be indicated by a single UCI-FUS toconserve signaling resources while improving time and frequencydiversity gains. Example 1500 shows a UCI-FUS 1504 that indicates afirst skipping pattern 1506 for the first two retransmissions and asecond skipping pattern 1508 for the last two retransmissions. The firstskipping pattern 1506 and the second skipping pattern 1508 in example1500 use half the resources (e.g., RBs) of a CG occasion for the MAC PDUbut hop frequencies or RBs over the total quantity of retransmissions.This improves frequency diversity and improves reliability whileconserving signaling resources. The network entity 1410 may enableand/or control the frequency hopping schemes. Time diversity may also beapplied.

Example 1502 shows that a single UCI-FUS 1510 may indicate the sameskipping pattern 1512 for not only initial transmissions but for anyretransmissions. The UE 1420 may transmit the UCI-FUS 1510 before thefirst initial transmission. In some aspects, the UCI-FUS 1510 mayinclude an additional bit that indicates that the retransmissions are toskip the resources of the same skipping pattern 1512. For example, ifthe bit is set to “1”, all of the multiple CG occasions (belonging to Kretransmissions) may have time and frequency resources that are skippedsimilarly. If the bit is set to “0”, the network entity 1410 may expectthe UCI-FUS 1510 to either include a skipping pattern (e.g., bitmap) forthe multiple CG occasions or expect that a UCI-FUS is to be transmittedbefore every CG occasion. Bitmaps may explicitly indicate skippedresources. Bitmaps may also indicate non-skipped resources such that theskipped resources can be derived from resources of a grant occasion (asum of the skipped resources and non-skipped resources equal a total ofthe resources of a grant occasion). That is, whether the bitmapexplicitly indicates skipped resources or non-skipped resources, thebitmap effectively indicates skipped resources. This also applies toskipping patterns that are indicated.

Note that while CG occasions are used as examples of the multiple grantoccasions, the multiple grant occasions may include grants for multiplePUSCH communications, which may be overallocated in anticipation ofincoming packets. The UCI-FUS may also be used for a dynamic grant ofmultiple grant occasions.

As indicated above, FIG. 15 provides some examples. Other examples maydiffer from what is described with regard to FIG. 15 .

FIG. 16 is a diagram illustrating an example process 1600 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 1600 is an example where the UE (e.g., UE 120, UE 1420) performsoperations associated with skipped resources for multiple grants.

As shown in FIG. 16 , in some aspects, process 1600 may includeselecting first resources to skip (skipped resources) in each grantoccasion of multiple grant occasions for communications on a physicaluplink channel (block 1610). For example, the UE (e.g., usingcommunication manager 1808 and/or selection component 1810 depicted inFIG. 18 ) may select first resources to skip in each grant occasion ofmultiple grant occasions for communications on a physical uplinkchannel, as described above.

As further shown in FIG. 16 , in some aspects, process 1600 may includetransmitting UCI that indicates the first resources or second resourcesthat are not to be skipped in each grant occasion of the multiple grantoccasions (block 1620). For example, the UE (e.g., using communicationmanager 1808 and/or transmission component 1804 depicted in FIG. 18 )may transmit UCI that indicates the first resources or second resourcesthat are not to be skipped in each grant occasion of the multiple grantoccasions, as described above.

As further shown in FIG. 16 , in some aspects, process 1600 may includetransmitting the communications in the multiple grant occasions usingthe second resources and not the first resources (block 1630). Forexample, the UE (e.g., using communication manager 1808 and/ortransmission component 1804 depicted in FIG. 18 ) may transmit thecommunications in the multiple grant occasions using the secondresources and not the first resources, as described above.

Process 1600 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, the UCI indicates a quantity of the multiple grantoccasions with the first resources.

In a second aspect, alone or in combination with the first aspect,process 1600 includes transmitting a cancellation indication thatindicates that resources are no longer skipped in grant occasions, andtransmitting additional communications without skipping resources.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the first resources include one or more of timeresources or frequency resources.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, selecting the first resources in each grantoccasion includes receiving an indication of a skipping pattern or abitmap of the first resources in each grant occasion.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the UCI includes a bitmap that indicates thefirst resources in each grant occasion of the multiple grant occasions.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the UCI includes an index that corresponds to askipping pattern of the first resources in each grant occasion.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the UCI indicates one or more time andfrequency bitmaps for the first resources in a specified quantity ofretransmissions.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, a quantity of most significant bits inthe UCI indicate the one or more time and frequency bitmaps.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the UCI includes an index that corresponds tothe one or more time and frequency bitmaps.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the one or more time and frequency bitmaps areassociated with a frequency hopping scheme.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, transmitting the UCI includes transmittingthe UCI before an initial transmission in the multiple grant occasions,and the first resources apply to retransmissions in the multiple grantoccasions.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, the UCI includes a bit that indicateswhether the first resources apply to each of the multiple grantoccasions.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, the multiple grant occasions includeconfigured grant occasions.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, the multiple grant occasions includegrants for transmissions on a PUSCH.

Although FIG. 16 shows example blocks of process 1600, in some aspects,process 1600 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 16 .Additionally, or alternatively, two or more of the blocks of process1600 may be performed in parallel.

FIG. 17 is a diagram illustrating an example process 1700 performed, forexample, by a network entity, in accordance with the present disclosure.Example process 1700 is an example where the network entity (e.g., basestation 110, network entity 1410) performs operations associated withskipped resources for multiple grants.

As shown in FIG. 17 , in some aspects, process 1700 may includereceiving UCI that indicates first resources (skipped resources) orsecond resources (non-skipped resources) of multiple grant occasions,the first resources in each grant occasion being skipped forcommunications on a physical uplink channel and the second resources notbeing skipped (block 1710). For example, the network entity (e.g., usingcommunication manager 1908 and/or reception component 1902 depicted inFIG. 19 ) may receive UCI that indicates first resources or secondresources of multiple grant occasions, the first resources in each grantoccasion being skipped for communications on a physical uplink channeland the second resources not being skipped, as described above.

As further shown in FIG. 17 , in some aspects, process 1700 may includereceiving the communications in the multiple grant occasions (block1720). For example, the network entity (e.g., using communicationmanager 1908 and/or reception component 1902 depicted in FIG. 19 ) mayreceive the communications in the multiple grant occasions, as describedabove.

As further shown in FIG. 17 , in some aspects, process 1700 may includedecoding the communications in the second resources and not decoding thecommunications in the first resources based at least in part on the UCI(block 1730). For example, the network entity (e.g., using communicationmanager 1908 and/or decoding component 1910 depicted in FIG. 19 ) maydecode the communications in the second resources and not decode thecommunications in the first resources based at least in part on the UCI,as described above.

Process 1700 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, the UCI indicates a quantity of the multiple grantoccasions with the first resources.

In a second aspect, alone or in combination with the first aspect,process 1700 includes receiving a cancellation indication that indicatesthat resources are no longer skipped in grant occasions, and decodingadditional communications without skipping resources.

In a third aspect, alone or in combination with one or more of the firstand second aspects, process 1700 includes transmitting an indication ofa skipping pattern or bitmap of the first resources in each grantoccasion.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the UCI includes a bitmap that indicatesthe first resources in each grant occasion for the multiple grantoccasions, and decoding the communications includes skipping decoding inthe first resources.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the UCI includes an index that corresponds to askipping pattern of the first resources in each grant occasion, anddecoding the communications includes skipping decoding in the skippingpattern that corresponds to the index.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the UCI indicates one or more time and frequencybitmaps for the first resources in a specified quantity ofretransmissions, and decoding the communications includes skippingdecoding in the first resources for the specified quantity ofretransmissions.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the UCI includes an index that correspondsto the one or more time and frequency bitmaps.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, the one or more time and frequencybitmaps are associated with a frequency hopping scheme.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, receiving the UCI includes receiving the UCIbefore an initial transmission in the multiple grant occasions, anddecoding the communications includes skipping decoding in the firstresources for retransmissions in the multiple grant occasions.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the UCI includes a bit that indicates whether thefirst resources apply to each of the multiple grant occasions.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the multiple grant occasions includeconfigured grant occasions.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, the multiple grant occasions includegrants for transmissions on a PUSCH.

Although FIG. 17 shows example blocks of process 1700, in some aspects,process 1700 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 17 .Additionally, or alternatively, two or more of the blocks of process1700 may be performed in parallel.

FIG. 18 is a diagram of an example apparatus 1800 for wirelesscommunication, in accordance with the present disclosure. The apparatus1800 may be a UE (e.g., UE 120, UE 1420), or a UE may include theapparatus 1800. In some aspects, the apparatus 1800 includes a receptioncomponent 1802 and a transmission component 1804, which may be incommunication with one another (for example, via one or more busesand/or one or more other components). As shown, the apparatus 1800 maycommunicate with another apparatus 1806 (such as a UE, a base station,or another wireless communication device) using the reception component1802 and the transmission component 1804. As further shown, theapparatus 1800 may include the communication manager 1808. Thecommunication manager 1808 may control and/or otherwise manage one ormore operations of the reception component 1802 and/or the transmissioncomponent 1804. In some aspects, the communication manager 1808 mayinclude one or more antennas, a modem, a controller/processor, a memory,or a combination thereof, of the UE described in connection with FIG. 2. The communication manager 1808 may be, or be similar to, thecommunication manager 140 depicted in FIGS. 1 and 2 . For example, insome aspects, the communication manager 1808 may be configured toperform one or more of the functions described as being performed by thecommunication manager 140. In some aspects, the communication manager1808 may include the reception component 1802 and/or the transmissioncomponent 1804. The communication manager 1808 may include a selectioncomponent 1810, among other examples.

In some aspects, the apparatus 1800 may be configured to perform one ormore operations described herein in connection with FIGS. 1-15 .Additionally, or alternatively, the apparatus 1800 may be configured toperform one or more processes described herein, such as process 1600 ofFIG. 16 . In some aspects, the apparatus 1800 and/or one or morecomponents shown in FIG. 18 may include one or more components of the UEdescribed in connection with FIG. 2 . Additionally, or alternatively,one or more components shown in FIG. 18 may be implemented within one ormore components described in connection with FIG. 2 . Additionally, oralternatively, one or more components of the set of components may beimplemented at least in part as software stored in a memory. Forexample, a component (or a portion of a component) may be implemented asinstructions or code stored in a non-transitory computer-readable mediumand executable by a controller or a processor to perform the functionsor operations of the component.

The reception component 1802 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 1806. The reception component1802 may provide received communications to one or more other componentsof the apparatus 1800. In some aspects, the reception component 1802 mayperform signal processing on the received communications (such asfiltering, amplification, demodulation, analog-to-digital conversion,demultiplexing, deinterleaving, de-mapping, equalization, interferencecancellation, or decoding, among other examples), and may provide theprocessed signals to the one or more other components of the apparatus1800. In some aspects, the reception component 1802 may include one ormore antennas, a modem, a demodulator, a MIMO detector, a receiveprocessor, a controller/processor, a memory, or a combination thereof,of the UE described in connection with FIG. 2 .

The transmission component 1804 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 1806. In some aspects, one or moreother components of the apparatus 1800 may generate communications andmay provide the generated communications to the transmission component1804 for transmission to the apparatus 1806. In some aspects, thetransmission component 1804 may perform signal processing on thegenerated communications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 1806. In some aspects, the transmission component 1804may include one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the UE described in connection with FIG. 2 . Insome aspects, the transmission component 1804 may be co-located with thereception component 1802 in a transceiver.

The selection component 1810 may select first resources (skippedresources) in each grant occasion to skip of multiple grant occasionsfor communications on a physical uplink channel. The transmissioncomponent 1804 may transmit UCI that indicates the first resources orsecond resources (non-skipped resources) that are not to be skipped ineach grant occasion of the multiple grant occasions. The transmissioncomponent 1804 may transmit the communications in the multiple grantoccasions using the second resources and not using the first resources.

The transmission component 1804 may transmit a cancellation indicationthat indicates that the first resources are no longer skipped in grantoccasions. The transmission component 1804 may transmit additionalcommunications without skipping resources.

The number and arrangement of components shown in FIG. 18 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 18 . Furthermore, two or more components shownin FIG. 18 may be implemented within a single component, or a singlecomponent shown in FIG. 18 may be implemented as multiple, distributedcomponents. Additionally, or alternatively, a set of (one or more)components shown in FIG. 18 may perform one or more functions describedas being performed by another set of components shown in FIG. 18 .

FIG. 19 is a diagram of an example apparatus 1900 for wirelesscommunication, in accordance with the present disclosure. The apparatus1900 may be a network entity (e.g., a base station 110, network entity1410), or a network entity may include the apparatus 1900. In someaspects, the apparatus 1900 includes a reception component 1902 and atransmission component 1904, which may be in communication with oneanother (for example, via one or more buses and/or one or more othercomponents). As shown, the apparatus 1900 may communicate with anotherapparatus 1906 (such as a UE, a base station, or another wirelesscommunication device) using the reception component 1902 and thetransmission component 1904. As further shown, the apparatus 1900 mayinclude the communication manager 1908. The communication manager 1908may control and/or otherwise manage one or more operations of thereception component 1902 and/or the transmission component 1904. In someaspects, the communication manager 1908 may include one or moreantennas, a modem, a controller/processor, a memory, or a combinationthereof, of the network entity described in connection with FIG. 2 . Thecommunication manager 1908 may be, or be similar to, the communicationmanager 150 depicted in FIGS. 1 and 2 . For example, in some aspects,the communication manager 1908 may be configured to perform one or moreof the functions described as being performed by the communicationmanager 150. In some aspects, the communication manager 1908 may includethe reception component 1902 and/or the transmission component 1904. Thecommunication manager 1908 may include a decoding component 1910, amongother examples.

In some aspects, the apparatus 1900 may be configured to perform one ormore operations described herein in connection with FIGS. 1-15 .Additionally, or alternatively, the apparatus 1900 may be configured toperform one or more processes described herein, such as process 1700 ofFIG. 17 . In some aspects, the apparatus 1900 and/or one or morecomponents shown in FIG. 19 may include one or more components of thenetwork entity described in connection with FIG. 2 . Additionally, oralternatively, one or more components shown in FIG. 19 may beimplemented within one or more components described in connection withFIG. 2 . Additionally, or alternatively, one or more components of theset of components may be implemented at least in part as software storedin a memory. For example, a component (or a portion of a component) maybe implemented as instructions or code stored in a non-transitorycomputer-readable medium and executable by a controller or a processorto perform the functions or operations of the component.

The reception component 1902 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 1906. The reception component1902 may provide received communications to one or more other componentsof the apparatus 1900. In some aspects, the reception component 1902 mayperform signal processing on the received communications (such asfiltering, amplification, demodulation, analog-to-digital conversion,demultiplexing, deinterleaving, de-mapping, equalization, interferencecancellation, or decoding, among other examples), and may provide theprocessed signals to the one or more other components of the apparatus1900. In some aspects, the reception component 1902 may include one ormore antennas, a modem, a demodulator, a MIMO detector, a receiveprocessor, a controller/processor, a memory, or a combination thereof,of the network entity described in connection with FIG. 2 .

The transmission component 1904 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 1906. In some aspects, one or moreother components of the apparatus 1900 may generate communications andmay provide the generated communications to the transmission component1904 for transmission to the apparatus 1906. In some aspects, thetransmission component 1904 may perform signal processing on thegenerated communications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 1906. In some aspects, the transmission component 1904may include one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the network entity described in connection withFIG. 2 . In some aspects, the transmission component 1904 may beco-located with the reception component 1902 in a transceiver.

The reception component 1902 may receive UCI that indicates firstresources (skipped resources) or second resources (non-skippedresources) in each grant occasion of multiple grant occasions, the firstresources in each grant occasion being skipped for communications on aphysical uplink channel and the second resources not being skipped. Thereception component 1902 may receive the communications in the multiplegrant occasions. The decoding component 1910 may decode thecommunications in the second resources and not decoding thecommunications in the first resources based at least in part on the UCI.

The reception component 1902 may receive a cancellation indication thatindicates that resources are no longer skipped in grant occasions. Thedecoding component 1910 may decode additional communications withoutskipping resources.

The transmission component 1904 may transmit an indication of a skippingpattern or bitmap of the first resources in each grant occasion.

The number and arrangement of components shown in FIG. 19 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 19 . Furthermore, two or more components shownin FIG. 19 may be implemented within a single component, or a singlecomponent shown in FIG. 19 may be implemented as multiple, distributedcomponents. Additionally, or alternatively, a set of (one or more)components shown in FIG. 19 may perform one or more functions describedas being performed by another set of components shown in FIG. 19 .

The following provides an overview of some Aspects of the presentdisclosure:

Aspect 1: A method of wireless communication performed by a userequipment (UE), comprising: selecting first resources to skip in eachgrant occasion of multiple grant occasions for communications on aphysical uplink channel; transmitting uplink control information (UCI)that indicates the first resources or second resources that are not tobe skipped in each grant occasion of the multiple grant occasions; andtransmitting the communications in the multiple grant occasions usingthe second resources and not the first resources.

Aspect 2: The method of Aspect 1, wherein the UCI indicates a quantityof the multiple grant occasions.

Aspect 3: The method of Aspect 1 or 2, further comprising: transmittinga cancellation indication that indicates that the first resources are nolonger skipped in grant occasions; and transmitting additionalcommunications without skipping resources.

Aspect 4: The method of any of Aspects 1-3, wherein the first resourcesinclude one or more of time resources or frequency resources.

Aspect 5: The method of any of Aspects 1-4, wherein selecting the firstresources in each grant occasion includes receiving an indication of askipping pattern or a bitmap of the first resources in each grantoccasion.

Aspect 6: The method of any of Aspects 1-5, wherein the UCI includes abitmap that indicates the first resources in each grant occasion of themultiple grant occasions.

Aspect 7: The method of any of Aspects 1-5, wherein the UCI includes anindex that corresponds to a skipping pattern of the first resources ineach grant occasion.

Aspect 8: The method of any of Aspects 1-7, wherein the UCI indicatesone or more time and frequency bitmaps for the first resources in aspecified quantity of retransmissions.

Aspect 9: The method of Aspect 8, wherein a quantity of most significantbits in the UCI indicate the one or more time and frequency bitmaps.

Aspect 10: The method of Aspect 8, wherein the UCI includes an indexthat corresponds to the one or more time and frequency bitmaps.

Aspect 11: The method of any of Aspects 8-10, wherein the one or moretime and frequency bitmaps are associated with a frequency hoppingscheme.

Aspect 12: The method of any of Aspects 1-11, wherein transmitting theUCI includes transmitting the UCI before an initial transmission in themultiple grant occasions, and wherein the first resources apply toretransmissions in the multiple grant occasions.

Aspect 13: The method of Aspect 12, wherein the UCI includes a bit thatindicates whether the first resources apply to each of the multiplegrant occasions.

Aspect 14: The method of any of Aspects 1-13, wherein the multiple grantoccasions include configured grant occasions.

Aspect 15: The method of any of Aspects 1-14, wherein the multiple grantoccasions include grants for transmissions on a physical uplink sharedchannel.

Aspect 16: A method of wireless communication performed by a networkentity, comprising: receiving uplink control information (UCI) thatindicates first resources or second resources of multiple grantoccasions, the first resources in each grant occasion being skipped forcommunications on a physical uplink channel and the second resources notbeing skipped; receiving the communications in the multiple grantoccasions; and decoding the communications in the second resources andnot decoding the communications in the first resources based at least inpart on the UCI.

Aspect 17: The method of Aspect 16, wherein the UCI indicates a quantityof the multiple grant occasions.

Aspect 18: The method of Aspect 16 or 17, further comprising: receivinga cancellation indication that indicates that the first resources are nolonger skipped in grant occasions; and decoding additionalcommunications without skipping resources.

Aspect 19: The method of any of Aspects 16-18, further comprisingtransmitting an indication of a skipping pattern or bitmap of the firstresources in each grant occasion.

Aspect 20: The method of any of Aspects 16-19, wherein the UCI includesa bitmap that indicates the first resources in each grant occasion forthe multiple grant occasions, and wherein decoding the communicationsincludes skipping decoding in the first resources.

Aspect 21: The method of any of Aspects 16-20, wherein the UCI includesan index that corresponds to a skipping pattern of the first resourcesin each grant occasion, and wherein decoding the communications includesskipping decoding in the skipping pattern that corresponds to the index.

Aspect 22: The method of any of Aspects 16-21, wherein the UCI indicatesone or more time and frequency bitmaps for the first resources in aspecified quantity of retransmissions, and wherein decoding thecommunications includes skipping decoding in the first resources for thespecified quantity of retransmissions.

Aspect 23: The method of Aspect 22, wherein the UCI includes an indexthat corresponds to the one or more time and frequency bitmaps.

Aspect 24: The method of Aspect 22 or 23, wherein the one or more timeand frequency bitmaps are associated with a frequency hopping scheme.

Aspect 25: The method of any of Aspects 16-24, wherein receiving the UCIincludes receiving the UCI before an initial transmission in themultiple grant occasions, and wherein decoding the communicationsincludes skipping decoding in the first resources for retransmissions inthe multiple grant occasions.

Aspect 26: The method of Aspect 25, wherein the UCI includes a bit thatindicates whether the first resources apply to each of the multiplegrant occasions.

Aspect 27: The method of any of Aspects 16-26, wherein the multiplegrant occasions include configured grant occasions.

Aspect 28: The method of any of Aspects 16-27, wherein the multiplegrant occasions include grants for transmissions on a physical uplinkshared channel.

Aspect 29: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects1-28.

Aspect 30: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 1-28.

Aspect 31: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 1-28.

Aspect 32: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 1-28.

Aspect 33: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 1-28.

The foregoing disclosure provides illustration and description but isnot intended to be exhaustive or to limit the aspects to the preciseforms disclosed. Modifications and variations may be made in light ofthe above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construedas hardware and/or a combination of hardware and software. “Software”shall be construed broadly to mean instructions, instruction sets, code,code segments, program code, programs, subprograms, software modules,applications, software applications, software packages, routines,subroutines, objects, executables, threads of execution, procedures,and/or functions, among other examples, whether referred to as software,firmware, middleware, microcode, hardware description language, orotherwise. As used herein, a “processor” is implemented in hardwareand/or a combination of hardware and software. It will be apparent thatsystems and/or methods described herein may be implemented in differentforms of hardware and/or a combination of hardware and software. Theactual specialized control hardware or software code used to implementthese systems and/or methods is not limiting of the aspects. Thus, theoperation and behavior of the systems and/or methods are describedherein without reference to specific software code, since those skilledin the art will understand that software and hardware can be designed toimplement the systems and/or methods based, at least in part, on thedescription herein.

As used herein, “satisfying a threshold” may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, not equal to the threshold, or thelike.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. Many of thesefeatures may be combined in ways not specifically recited in the claimsand/or disclosed in the specification. The disclosure of various aspectsincludes each dependent claim in combination with every other claim inthe claim set. As used herein, a phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination withmultiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b,a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b,and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterms “set” and “group” are intended to include one or more items andmay be used interchangeably with “one or more.” Where only one item isintended, the phrase “only one” or similar language is used. Also, asused herein, the terms “has,” “have,” “having,” or the like are intendedto be open-ended terms that do not limit an element that they modify(e.g., an element “having” A may also have B). Further, the phrase“based on” is intended to mean “based, at least in part, on” unlessexplicitly stated otherwise. Also, as used herein, the term “or” isintended to be inclusive when used in a series and may be usedinterchangeably with “and/or,” unless explicitly stated otherwise (e.g.,if used in combination with “either” or “only one of”).

What is claimed is:
 1. A user equipment (UE) for wireless communication,comprising: a memory; and one or more processors, coupled to the memory,configured to: select first resources to skip in each grant occasion ofmultiple grant occasions for communications on a physical uplinkchannel; transmit uplink control information (UCI) that indicates thefirst resources or second resources that are not to be skipped in eachgrant occasion of the multiple grant occasions; and transmit thecommunications in the multiple grant occasions using the secondresources and not the first resources.
 2. The UE of claim 1, wherein theUCI indicates a quantity of the multiple grant occasions.
 3. The UE ofclaim 1, wherein the one or more processors are configured to: transmita cancellation indication that indicates that the first resources are nolonger skipped in grant occasions; and transmit additionalcommunications without skipping resources.
 4. The UE of claim 1, whereinthe first resources include one or more of time resources or frequencyresources.
 5. The UE of claim 1, wherein the one or more processors, toselect the first resources in each grant occasion, are configured toreceive an indication of a skipping pattern or a bitmap of the firstresources in each grant occasion.
 6. The UE of claim 1, wherein the UCIincludes a bitmap that indicates the first resources in each grantoccasion of the multiple grant occasions.
 7. The UE of claim 1, whereinthe UCI includes an index that corresponds to a skipping pattern of thefirst resources in each grant occasion.
 8. The UE of claim 1, whereinthe UCI indicates one or more time and frequency bitmaps for the firstresources in a specified quantity of retransmissions.
 9. The UE of claim8, wherein a quantity of most significant bits in the UCI indicate theone or more time and frequency bitmaps.
 10. The UE of claim 8, whereinthe UCI includes an index that corresponds to the one or more time andfrequency bitmaps.
 11. The UE of claim 8, wherein the one or more timeand frequency bitmaps are associated with a frequency hopping scheme.12. The UE of claim 1, wherein the one or more processors, to transmitthe UCI, are configured to transmit the UCI before an initialtransmission in the multiple grant occasions, and wherein the firstresources apply to retransmissions in the multiple grant occasions. 13.The UE of claim 12, wherein the UCI includes a bit that indicateswhether the first resources apply to each of the multiple grantoccasions.
 14. The UE of claim 1, wherein the multiple grant occasionsinclude configured grant occasions.
 15. The UE of claim 1, wherein themultiple grant occasions include grants for transmissions on a physicaluplink shared channel.
 16. A network entity for wireless communication,comprising: a memory; and one or more processors, coupled to the memory,configured to: receive uplink control information (UCI) that indicatesfirst resources or second resources of multiple grant occasions, thefirst resources in each grant occasion being skipped for communicationson a physical uplink channel and the second resources not being skipped;receive the communications in the multiple grant occasions; and decodethe communications in the second resources and not decode thecommunications in the first resources based at least in part on the UCI.17. The network entity of claim 16, wherein the UCI indicates a quantityof the multiple grant occasions.
 18. The network entity of claim 16,wherein the one or more processors are configured to: receive acancellation indication that indicates that the first resources are nolonger skipped in grant occasions; and decode additional communicationswithout skipping resources.
 19. The network entity of claim 16, whereinthe one or more processors are configured to transmit an indication of askipping pattern or bitmap of the first resources in each grantoccasion.
 20. The network entity of claim 16, wherein the UCI includes abitmap that indicates the first resources in each grant occasion for themultiple grant occasions, and wherein the one or more processors, todecode the communications, are configured to skip decoding in the firstresources.
 21. The network entity of claim 16, wherein the UCI includesan index that corresponds to a skipping pattern of the first resourcesin each grant occasion, and wherein the one or more processors, todecode the communications, are configured to skip decoding in the firstpattern that corresponds to the index.
 22. The network entity of claim16, wherein the UCI indicates one or more time and frequency bitmaps forthe first resources in a specified quantity of retransmissions, andwherein the one or more processors, to decode the communications, areconfigured to skip decoding in the first resources for the specifiedquantity of retransmissions.
 23. The network entity of claim 22, whereinthe UCI includes an index that corresponds to the one or more time andfrequency bitmaps.
 24. The network entity of claim 22, wherein the oneor more time and frequency bitmaps are associated with a frequencyhopping scheme.
 25. The network entity of claim 16, wherein the one ormore processors, to receive the UCI, are configured to receive the UCIbefore an initial transmission in the multiple grant occasions, andwherein the one or more processors, to decode the communications, areconfigured to skip decoding in the first resources for retransmissionsin the multiple grant occasions.
 26. The network entity of claim 25,wherein the UCI includes a bit that indicates whether the firstresources apply to each of the multiple grant occasions.
 27. The networkentity of claim 16, wherein the multiple grant occasions includeconfigured grant occasions.
 28. The network entity of claim 16, whereinthe multiple grant occasions include grants for transmissions on aphysical uplink shared channel.
 29. A method of wireless communicationperformed by a user equipment (UE), comprising: selecting firstresources to skip in each grant occasion of multiple grant occasions forcommunications on a physical uplink channel; transmitting uplink controlinformation (UCI) that indicates the first resources or second resourcesthat are not to be skipped in each grant occasion of the multiple grantoccasions; and transmitting the communications in the multiple grantoccasions using the second resources and not the first resources.
 30. Amethod of wireless communication performed by a network entity,comprising: receiving uplink control information (UCI) that indicatesfirst resources or second resources of multiple grant occasions, thefirst resources in each grant occasion being skipped for communicationson a physical uplink channel and the second resources not being skipped;receiving the communications in the multiple grant occasions; anddecoding the communications in the second resources and not decoding thecommunications in the first resources based at least in part on the UCI.